Skip to main content
Version: 2.0

OKR Achievement Rate

Objectives and Key Results (OKRs) are a powerful tool for aligning teams and driving progress. However, a common pitfall is the pursuit of a 100% achievement rate. This article explores why that goal is counterproductive and how to cultivate a more effective approach.

For two decades, I’ve helped engineering teams ship products, navigate technical debt, and, crucially, set and track Objectives and Key Results (OKRs). I've seen countless teams fall into the trap of striving for a perfect 100% OKR achievement rate. And I’m here to tell you: it's a terrible goal, and actively hinders growth.

It's not about abandoning accountability; it’s about recognizing that truly ambitious OKRs, the kind that move the needle, shouldn’t be fully achieved. Let’s dive into why, and how to recalibrate your approach to metrics and evaluation.

The Problem with Perfection​

The allure of 100% achievement is understandable. It feels good. It's easy to report. It reinforces a narrative of success. But here's the truth: a consistently high achievement rate signals one of two things:

  1. You're Sandbagging: The OKRs weren’t ambitious enough. You essentially set goals you knew you could hit. While it might look good on paper, you're missing opportunities for stretch and innovation. You’ve traded genuine progress for a comfortable illusion of success.
  2. Your Objectives Aren’t Truly Objectives: Objectives should be qualitative, inspiring, and directional. Key Results are the measurable components that tell you if you're heading in the right direction. If your KRs are simply tasks, you're confusing output with outcome. A completed task isn't an objective; it's a step towards achieving one.

I remember leading a team where we consistently hit 90-100% on our OKRs. It felt great… until we realized we were optimizing for hitting the numbers instead of solving customer problems. We’d break down ambitious goals into tiny, easily achievable key results, effectively neutering the original intent. It took a frank conversation and a deliberate shift towards more challenging, less predictable KRs to break that cycle.

The Sweet Spot: 60-70% Achievement​

Now, let’s talk about a more realistic – and effective – target: 60-70% achievement. This range represents a balance between ambitious goals and realistic execution. It’s important to note that this range is based on my experience and observations across multiple teams – it’s not a scientifically proven number, but a practical guideline developed through years of working with engineering leaders.

  • It Allows for Learning: When you aim for ambitious goals and fall slightly short, you’re forced to analyze why. What obstacles did we encounter? What assumptions were incorrect? This post-mortem analysis is invaluable for future planning.
  • It Encourages Innovation: A challenging target fosters a culture of experimentation. Teams are more likely to explore creative solutions when they know they're not penalized for taking calculated risks.
  • It Differentiates Between Effort and Impact: Hitting 60-70% requires focused effort on the right things. It forces prioritization and ruthlessly cuts away tasks that don’t contribute to the objective.

Beyond the Percentage: Qualitative Review​

While the 60-70% guideline is useful, don't treat it as a rigid rule. Numbers alone don't tell the whole story. Complement your quantitative analysis with a thorough qualitative review:

  • What did we learn? Even if we didn’t hit all our KRs, what valuable insights did we gain?
  • What unexpected benefits emerged? Sometimes, the journey towards an objective reveals unforeseen opportunities.
  • What barriers prevented us from achieving more? Were these internal (process, skill gaps) or external (market conditions, dependencies)?
  • Were our assumptions validated? Did we accurately predict the impact of our efforts?

This qualitative review should be a safe space for honest feedback and constructive criticism. Encourage your team to share their learnings, even if they involve failures.

Shifting the Mindset: From "Hitting Numbers" to "Driving Impact"​

The biggest challenge isn’t changing the numbers; it’s changing the mindset. As engineering leaders, we need to emphasize that the purpose of OKRs isn't to achieve a perfect score; it’s to drive meaningful results.

Here’s how:

  • Focus on the "Why": Clearly articulate the strategic rationale behind each objective. Connect it to the company’s overall vision.
  • Celebrate Learning, Not Just Success: Recognize and reward teams for taking risks, experimenting, and sharing their learnings, even if they fall short of their goals.
  • Lead by Example: Be open about your own failures and lessons learned. Show your team that it’s okay to take calculated risks and learn from mistakes.

Therefore, shift your focus away from achieving 100%. Embrace the 60-70% sweet spot, and focus on driving real, measurable results. Your team – and your company – will thank you.

This week, review your team’s current OKRs and identify opportunities to make them more ambitious and challenging. Consider scheduling a team discussion to explore the potential benefits of shifting your mindset from “hitting numbers” to “achieving results.”